Tagging subscribers to this area: @buyaa-n
Notify danmosemsft if you want to be subscribed.

@buyaa-n
I've changed the order of these two tests.

Note that I also had to removed "fixed='true'" from another test (FractionDigitsMismatch_Throws). It wasn't needed for this test, but at the time the test was created, it was not honored. Therefore, I hadn't noticed the error. With the fix to this issue, that test started failing due to a different exception being thrown now that the fixed facet was honored.

I've changed the order of these two tests.

Note that I also had to removed "fixed='true'" from another test (FractionDigitsMismatch_Throws). It wasn't needed for this test, but at the time the test was created, it was not honored. Therefore, I hadn't noticed the error. With the fix to this issue, that test started failing due to a different exception being thrown now that the fixed facet was honored.

Thank you @mrj001, the tests might fail on full framework too, might need to add SkipOnTargetFramework

@buyaa-n
I've added the SkipOnTargetFramework attribute to FractionDigitsFacetBaseFixed_Throws, as .NET Framework 4.7.2 did not throw the required exception.

.NET Framework 4.7.2 is also throwing the "totalDigits" error message in the FractionDigitsMismatch_Throws test instead of the "fractionDigits" error message. This would cause that test to fail under 47.2 as well. I've taken the liberty of adding the SkipOnTargetFramework attribute here as well, even though it is outside the scope of this pull request.

I've added the SkipOnTargetFramework attribute to FractionDigitsFacetBaseFixed_Throws, as .NET Framework 4.7.2 did not throw the required exception.

.NET Framework 4.7.2 is also throwing the "totalDigits" error message in the FractionDigitsMismatch_Throws test instead of the "fractionDigits" error message. This would cause that test to fail under 47.2 as well. I've taken the liberty of adding the SkipOnTargetFramework attribute here as well, even though it is outside the scope of this pull request.

Great, looks good, thank you @mrj001.

The CI legs showing still in progress were successfully finished in details on Azure Pipelines, gonna merge this PR